Developer CD Series 1997 January: Mac OS SDK/Dev.CD Jan 97 SDK2.toast/Development Kits (Disc 2)/OpenDoc Development Framework/ODF-Interest Archive/July 96/Re Part Server.10

Internet Message Format | 1996-07-10 | 1.5 KB | [TEXT/ttxt]

Subject:     Re: Part Server
Sent:        7/10/96 11:39 AM
Received:    7/10/96 11:51 AM
From:        Serge Froment, [e-mail]
Reply-To:    ODF Interest, [e-mail]
To:          OpenDoc Development Framework Discussion List, ODF-Interest@CILabs.

Thanks for your helpful information. I have more questions, though.

>- Create a shared library that has a callable C or SOM API
>- Make the shared libraries data fragment shared. Use globals to point at
>data structures that all parts and processes should share.
>- Clients call the C or SOM API
>- Optionally use the threads manager from within the shared library

With such a shared library, in which process will the data fragment live?
In which heap will a call to NewHandle allocate memory? Can I use temp
memory? If I crash inside the shared library, will the memory it allocated
be released?

If I use the thread manager, where will threads live, relative to
processes? This may be a dumb question, but I thought threads must belong
to a process.

>MacApp has been used to create background tasks, but there is no intrinsic
>support in the framework. I don't know about PowerPlant. I'm not sure you'd
>need an framework, anyhow. You probably don't want to create a fullblown
>app. You certainly don't need all of the menu, view, document stuff that
>the frameworks provide. You could probably roll your own with only a
>minimum of application code.

I obviously don't need menus, but I think MacApp has some nice stuff to
handle AppleEvents. Can I use that without using the remaining of MacApp?

Serge